[MeshModel] Kubernetes Ontology Browser #7465
Labels
issue/design required
Functional architecture
issue/willfix
This issue will be worked on
kind/feature
New major feature or request
Description
Network topologies and graph databases go hand-in-hand. The OpenAPI specifications for Kubernetes provides taxonomy, but augmenting a graph data model with formalized ontologies enables any number of capabilities, one of the more straightforward is the inferencing requisite for natural language processing, and consequently, a human-centric query / response interaction becomes becomes possible. More importantly, more advanced systems can be built when a graph data model of connected systems is upgraded to be a knowledge semantic graph.
Desired Behavior
Represent this ontology in a graph database and a #6665
Implementation
Using Reactjs, Golang, OpenNebula
Acceptance Tests
Deliverables (among other items):
Phase 1 Use Cases:
MeshModel
Other related implementations to reference and reuse:
Phase 2 Use Cases:
For the initial set of use cases, use the REST-based MeshModels API:
/api/meshmodels/models/components/?search=envoy&v1&apiversion=1
When POSTing, follow up with a GET.
FYI: Server Side Events (SSE) are used under /api/events.
Mockups
See https://www.figma.com/file/SMP3zxOjZztdOLtgN4dS2W/Meshery-UI?node-id=12835-37612&t=R391PMgNPxdKOFMK-4
Contributor Guides and Handbook
The text was updated successfully, but these errors were encountered: